samsam
Value identification and comparison functions
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): reinseth is a known ecosystem contributor (3124 days, 11 approved versions); transition from cjohansen appears to be a legitimate busterjs maintainer handoff with no code-level changes. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): reinseth has a clean track record (11 approved, 0 rejected); addition is consistent with legitimate project maintainer transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): samsam is a stable, mature utility in the busterjs ecosystem; long dormancy followed by a minor update is expected behavior for this type of package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 0 / 5 | |
| 1.2.1 | 0 / 5 | |
| 1.2.0 | 0 / 5 | |
| 1.1.3 | 0 / 5 | |
| 1.1.2 | 0 / 1 | |
| 1.1.1 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.1 | 0 / 1 | |
| 1.0.0 | 0 / 1 | |
| 0.1.1 | 1 / 1 | |
| 0.1.0 | 0 / 2 |
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2017-10-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-02-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-11-14. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.